Systems and methods for hit and run detection based on intelligent micro devices

ABSTRACT

A system, method, and computer-usable medium are disclosed for providing information relating to damage incurred by a vehicle in an accident. A first plurality of markers with a first set of identifiers is embedded in a coating applied to a component of a first vehicle and a second plurality of markers with a second set of identifiers is embedded in a coating applied to a component of a second vehicle. Markers from the first vehicle are transferred to the second vehicle upon impact during an accident. The transferred markers are read by a marker reader and then processed to determine the identity of the first vehicle.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.12/250,030, now U.S. Pat. No. 8,203,425, entitled “Systems and Methodsfor Run Detection Based on Intelligent Micro Devices,” by inventorsReynaldo Medina and Michael P. Bueche, Jr., filed on Oct. 13, 2008,describes exemplary methods and systems and is incorporated by referencein its entirety.

U.S. patent application Ser. No. 12/250,028, entitled “Systems andMethods for Run Detection Based on Intelligent Micro Devices,” byinventors Reynaldo Medina and Michael P. Bueche, Jr., filed on Oct. 13,2008, describes exemplary methods and systems and is incorporated byreference in its entirety.

U.S. patent application Ser. No. 12/250,031, entitled “Systems andMethods for Run Detection Based on Intelligent Micro Devices,” byinventors Reynaldo Medina and Michael P. Bueche, Jr., filed on Oct. 13,2008, describes exemplary methods and systems and is incorporated byreference in its entirety.

BACKGROUND

1. Field of the Disclosure

Embodiments of the disclosure relate in general to the field ofcomputers and similar technologies, and in particular to softwareutilized in this field. Still more particularly, it provides a system,method, and computer-usable medium for providing information relating todamage incurred by a vehicle in an accident.

2. Description of the Related Art

Automobile accidents are an all too common and unfortunate fact of life.In 2005, there were over 6,400,000 automobile accidents in the UnitedStates resulting in a financial cost of more than 230 billion dollars.In addition, 2.9 million people were injured and over 42,000 fatalitiesoccurred in the same year. Currently, over 100 people die every day inthe United States due to vehicle crashes, equating to one death every 13minutes.

Being involved in an automobile accident can be traumatic, withreactions ranging from poor concentration, nervousness, anxiety,irritability, to agitation, or even being in a state of shock. As aresult, the scene of an accident can be confusing to all involved,including eyewitnesses. Recalling what was seen and said, by whom and inwhat context, can prove problematic under the best of circumstances.Witnesses' memories fade as time passes, and the details of the accidentbecome vague. In some cases, a witness may even begin to rationalizewhat they believe they may or may not have witnessed. In addition,investigation of automobile accidents is often hampered by lack ofevidence, especially in the case of a hit-and-run accident involving twoautomobiles. Even if eyewitnesses happen to be present, theirrecollections may be unreliable. In other cases, there are noeyewitnesses at all, just damage to one or more vehicles, and in somecases, other property as well. All too often, there is no reliable wayto identify the automobile that was the cause of the hit and runaccident.

One issue relating to automobile accidents is the repair of damagedvehicles. Insurance claims adjusters are typically tasked with assessingthe damage to a vehicle, determining a reasonable cost to repair,providing a financial settlement for the repairs, and then certifyingthat the repairs were performed properly using legitimate parts.However, unscrupulous body shops have been known to use counterfeitparts to increase their profits. In some cases, the substitution ofthese counterfeit parts is not immediately apparent, but their use soonleads to dissatisfaction with the repairs. While such cases may be theexception, the traffic in counterfeit body parts is not inconsequential.In 1997, the Federal Trade Commission estimated that counterfeiting costthe global auto industry $12 billion, $3 billion of which is in theUnited States. It is the consensus of aftermarket parts manufacturersthat those estimates are far too conservative today. Worse yet are caseswhere the perpetrator of a hit and run accident, or an auto body repairshop, attempts to hide evidence of damage to the perpetrator's vehicle,which is a criminal act. Another related issue is the sale of repairedvehicles that have been damaged in an accident. In general, repairs of adamaged vehicle are reported and subsequently disclosed to a potentialbuyer by the seller. Currently, services such as CARFAX® provide ahistory of accident repairs and related information to prospectivebuyers of an automobile. However, such services are only as good as theinformation they are provided. Furthermore, not all accident repairs areproperly reported or recorded. Even when they are, there is no way forthe buyer to verify the provenance of the body parts used to repair theautomobile.

BRIEF SUMMARY

A system, method, and computer-usable medium are disclosed for providinginformation relating to damage incurred by a vehicle in an accident. Invarious embodiments, a plurality of markers is embedded in a coatingapplied to a component of a vehicle. As used herein, a marker is definedas any apparatus or group of technologies that comprises an identifierthat can be read by a reader. In various embodiments, the identifier ofthe marker may be a visual identifier such as a two dimensional barcode,an electromagnetic identifier, an electro luminescent identifier, or acarbon nanotube signature. In one embodiment, the marker comprises aradio frequency identification (RFID) tag that can be read by an RFIDtag reader. Likewise, a vehicle component is defined as any individualpart of, or sub-assembly of a vehicle, including but not limited tointernal and external body panels, structural and suspension components,and mechanical assemblies such as a drivetrain. In one embodiment, aplurality of markers is randomly applied to a vehicle component. Inanother embodiment, a plurality of markers is suspended within acoating, which is then applied to a component of a vehicle. In yetanother embodiment, each of a plurality of markers are applied to apredetermined location of a component of a vehicle and a coating is thenapplied to embed the markers in the coating.

In various embodiments, a first plurality of markers is embedded in acoating applied to a component of a first vehicle and a second pluralityof markers is embedded in a coating applied to a component of a secondvehicle. In these and other embodiments, the first vehicle may strikethe second vehicle in the course of an accident. In the case of ahit-and-run accident, the first vehicle may leave the scene of theaccident. In one embodiment, markers from the first vehicle are left atthe scene of the accident. In another embodiment, one or more markersfrom the first vehicle become transferred markers upon impact with thesecond vehicle. In one embodiment, markers from the first vehicle leftat the scene of the accident are read with a portable or handheld markerreader operated by an accident investigator. In another embodiment, thesecond vehicle is passed through a stationary marker reader to read thetransferred markers from the first vehicle. The marker identifiers readby the marker readers are then processed by a vehicle marker processingsystem, which comprises a marker analysis module.

In various embodiments, the vehicle marker processing system accessesone or more information repositories to determine the identity of thefirst vehicle. In one embodiment, prior damage and any related repairsto the second vehicle is determined by reading the identifier of thesecond vehicle's markers, which are then used to query a vehicle historysystem comprising a vehicle repair history information repository. Inone embodiment, the vehicle history information repository comprisesrepair history information cross-referenced to component informationprovided by one or more vehicle component manufacturers, each of whichmaintains a vehicle component information repository. In anotherembodiment, the vehicle marker processing system may access one or morevehicle component information repositories and cross-reference theinformation they provide to the information provided by the vehiclehistory system. In one embodiment, the information provided by each ofthe vehicle component information repositories is certified by acomponent certification system, which in turn comprises a componentcertification module and a component certification informationrepository. By comparing the information provided by the vehicle historysystem to the marker identifiers read by the marker readers, the vehiclemarker processing system can differentiate between reported damage andrepairs and apparent new damage caused by the first vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

Selected embodiments of the disclosure may be understood, and itsnumerous objects and features obtained, when the following detaileddescription is considered in conjunction with the following drawings, inwhich:

FIG. 1 depicts an exemplary client information processing system (IPS)in which embodiments of the disclosure may be implemented;

FIG. 2 is a simplified illustration of a plurality of markers embeddedin a coating applied to a vehicle component in accordance with anembodiment of the disclosure;

FIG. 3 is a simplified illustration of a plurality of markers randomlyapplied to a vehicle component in accordance with an embodiment of thedisclosure;

FIG. 4 is a simplified illustration of a plurality of markers applied toa predetermined location on a vehicle component in accordance with anembodiment of the disclosure;

FIG. 5 is a simplified illustration of the application of a plurality ofmarkers applied to a predetermined location on a vehicle component inaccordance with an embodiment of the disclosure;

FIG. 6 is a simplified illustration of a vehicle marker processingsystem as implemented in accordance with an embodiment of thedisclosure;

FIG. 7 is a simplified illustration of a plurality of markers embeddedin a coating applied to a plurality of vehicle components in accordancewith an embodiment of the disclosure;

FIG. 8 is a simplified illustration of a stationary marker reader asimplemented in an embodiment of the disclosure;

FIG. 9 is a generalized flowchart of the operation of a vehicle markerprocessing system as implemented in accordance with an embodiment of thedisclosure to provide vehicle accident information;

FIG. 10 is a simplified illustration of a stationary marker reader asimplemented in an embodiment of the disclosure to detect prior vehiclerepairs;

FIG. 11 is a simplified illustration of a stationary marker reader asimplemented in an embodiment of the disclosure to verify vehicle repairhistory;

FIG. 12 is a generalized flowchart of the operation of a vehicle markerprocessing system as implemented in accordance with an embodiment of thedisclosure to verify vehicle repair information; and

FIG. 13 is a generalized illustration of a vehicle repair history asimplemented in accordance with an embodiment of the invention.

DETAILED DESCRIPTION

A method, system and computer-usable medium are disclosed for providinginformation relating to damage incurred by a vehicle in an accident. Aswill be appreciated by one skilled in the art, the disclosure may beembodied as a method, system, or computer program product. Accordingly,various embodiments may be implemented entirely in hardware, entirely insoftware (including firmware, resident software, micro-code, etc.) or inan embodiment combining software and hardware. These various embodimentsmay all generally be referred to herein as a “circuit,” “module,” or“system.”

For purposes of this disclosure, an information processing system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, orutilize any form of information, intelligence, or data for business,scientific, control, or other purposes. For example, an informationprocessing system may be a personal computer, a personal digitalassistant (PDA), a wirelessly-enabled mobile telephone, a server, anetwork storage device, or any other suitable device and may vary insize, shape, performance, functionality, and price. The informationprocessing system may include random access memory (RAM), one or moreprocessing resources such as a central processing unit (CPU) or hardwareor software control logic, read only memory (ROM), and/or other types ofnonvolatile memory. Additional components of the information processingsystem may include one or more disk drives, one or more network portsfor communicating with external devices, as well as various input andoutput (I/O) devices, such as a keyboard, a mouse, and a video display.The information processing system may also include one or more busesoperable to transmit communications between the various hardwarecomponents.

Additionally, various embodiments may take the form of a computerprogram product on a computer-usable storage medium havingcomputer-usable program code embodied in the medium. Any suitablecomputer usable or computer readable medium may be utilized. Thecomputer-usable or computer-readable medium may be, for example, but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, device, or propagation medium. Anon-exhaustive list of more specific examples of the computer-readablemedium would include the following: an electrical connection having oneor more wires, an optical fiber, a transmission media such as thosesupporting the Internet or an intranet, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a magnetic storage device, a portable computerdiskette, a hard disk, an optical storage device, a portable compactdisc read-only memory (CD-ROM), or a digital versatile disk (DVD). Notethat the computer-usable or computer-readable medium could even be paperor another suitable medium upon which the program is printed, as theprogram can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner and then stored in a computermemory. In the context of this document, a computer-usable orcomputer-readable medium may be any medium that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.The computer-usable medium may include a propagated data signal with thecomputer-usable program code embodied therein, either in baseband or aspart of a carrier wave. The computer usable program code may betransmitted using any appropriate medium, including but not limited tothe Internet, wireline, optical fiber cable, wireless, radio frequency(RF), etc.

Computer program code for carrying out operations in various embodimentsmay be written in an object oriented programming language such as Java,Smalltalk, C++ or the like. However, the computer program code forcarrying out operations in various embodiments may also be written inconventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through a local area network (LAN), awide area network (WAN), a wireless local area network (WLAN), awireless wide area network (WWAN), a or personal area network (PAN). Inaddition, the connection may be made to an external computer (forexample, through the Internet using an Internet Service Provider) usingany combination of telecommunication technologies and protocols operableto establish a network connection for the exchange of information.

Embodiments of the disclosure are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products. It will be understood that eachblock of the flowchart illustrations and/or block diagrams, andcombinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer program instructions. Thesecomputer program instructions may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer, informationprocessing system, or other programmable data processing apparatus, tofunction in a particular manner such that the instructions stored in thecomputer-readable memory produce an article of manufacture includinginstruction means which implement the function/act specified in theflowchart and/or block diagram block or blocks. The computer programinstructions may also be loaded onto a computer or other programmabledata processing apparatus to cause a series of operational steps to beperformed on the computer or other programmable apparatus to produce acomputer implemented process such that the instructions which execute onthe computer or other programmable apparatus provide steps forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

FIG. 1 is a generalized block diagram of an exemplary client informationprocessing system (IPS) 100 in which various embodiments may beutilized. Client IPS 100 includes a processor unit 102 that is coupledto one or more buses 134. A display controller 112, which controls adisplay 114, is also coupled to or more buses 134, along with peripheralcontroller 108, which controls one or more peripheral devices 110. Aninput/output (I/O) controller 116 affords communication with various I/Odevices, including a keyboard 118, a mouse 120, a floppy disk drive 122,a Compact Disk-Read Only Memory (CD-ROM) drive 124, a flash drive memory126, and one or more I/O ports 128. The format of the ports connected tothe I/O controller 116 may be any known to those skilled in the art ofcomputer architecture, including but not limited to Universal Serial Bus(USB) ports.

Client IPS 100 is able to communicate with a service provider server 164via a network 162 using a communications controller 130, which iscoupled to one or more buses 134. Network 162 may be the public switchedtelephone network (PSTN), an external network such as the publicInternet, an internal network such as an Ethernet-based local areanetwork (LAN), a Virtual Private Network (VPN) such as a corporateintranet, or any combination of telecommunication technologies andprotocols operable to establish a network connection for the exchange ofinformation. Using network 162, client IPS 100 is able to access serviceprovider server 164.

A storage controller 104 is also coupled to one or more buses 134.Storage controller 104 interfaces with storage disk or drive 106, whichmay comprise a magnetic storage device such as a hard disk or tapedrive. In various embodiments, storage disk or drive 106 populates asystem memory 136, which is also coupled to one or more buses 134. Datathat populates system memory 136 includes the client IPS 100 operatingsystem (OS) 138 and software programs 144.

OS 138 includes a shell 140 for providing transparent user access toresources such as software programs 144. Generally, shell 140 is aprogram that provides an interpreter and an interface between the userand the operating system. More specifically, shell 140 executes commandsthat are entered into a command line user interface or from a file.Thus, shell 140 (as it is called in UNIX®), also called a commandprocessor in Windows®, is generally the highest level of the operatingsystem software hierarchy and serves as a command interpreter. The shellprovides a system prompt, interprets commands entered by keyboard,mouse, or other user input media, and sends the interpreted command(s)to the appropriate lower levels of the operating system (e.g., a kernel142) for processing. While shell 140 generally is a text-based,line-oriented user interface, various embodiments may also support otheruser interface modes, such as graphical, voice, gestural, etc. Asdepicted, OS 138 also includes kernel 142, which includes lower levelsof functionality for OS 138, including services used by other parts ofOS 138 and software programs 144, including memory management, processand task management, disk management, and mouse and keyboard management.

Software programs 144 may include a communications stack 146, browser156, email client 158, and other programs 160. The communications stack146 is operable to implement any communication protocol enabling variousembodiments of the disclosure. Browser 156 includes program modules andinstructions enabling a World Wide Web (WWW) client (i.e., IPS 100) tosend and receive network messages to the Internet using HyperTextTransfer Protocol (HTTP) messaging, thus enabling communication withservice provider server 164. Software programs 144 also include a markeranalysis module 148. The marker analysis module 148 includes computerexecutable instructions for implementing the processes described inFIGS. 2-13 described hereinbelow. In one embodiment, client IPS 100 isable to download the computer executable instructions of the markeranalysis module 148 from a service provider server 164 located at aremote location. In another embodiment, the computer executableinstructions of the marker analysis module 148 are provided by a serviceprovider as a service, such as a Web service implemented on aService-Oriented Architecture (SOA), to the client IPS 100 on anon-demand basis.

The hardware elements depicted in client IPS 100 are not intended to beexhaustive, but rather are representative to highlight components usedby the disclosure. For instance, client IPS 100 may include alternatememory storage devices such as magnetic cassettes, Digital VersatileDisks (DVDs), Bernoulli cartridges, and the like. These and othervariations are intended to be within the spirit and scope of thedisclosure.

FIG. 2 is a simplified illustration of a plurality of markers 202embedded in a coating 204 applied to a vehicle component 206 inaccordance with an embodiment of the disclosure. In various embodiments,a plurality of markers 202 are embedded in a coating 204 applied to acomponent 206 of a vehicle. As used herein, a marker is defined as anyapparatus or group of technologies that comprises an identifier that canbe read by a reader. In various embodiments, the identifier of themarker may be a visual identifier such as a two dimensional barcode, anelectromagnetic identifier, an electro luminescent identifier, or acarbon nanotube signature. Many such embodiments are possible and theforegoing are presented as examples and are not intended to limit thespirit, scope, or intent of the disclosure.

In one embodiment, the marker 202 comprises a radio frequencyidentification (RFID) tag that can be read by an RFID tag reader. Invarious embodiments, the RFID may be passive, active, or semi-passive.Passive RFID tags have no internal power supply. Instead, an electricalcurrent induced in the RFID's antenna provides power to transmit aresponse. Passive RFID tags typically have a practical read distance ofapproximately four inches. Currently, micro RFID tags are available thatmeasure as small as 0.05×0.05 mm. It will be apparent to those of skillin the art that such micro RFID tags are suitable for inclusion in thecoating of a vehicle component, in a fashion similar to how metal flakesare suspended in the color coat of an automobile's finish. In contrast,an active RFID tag has its own power source and may transmit at higherpower levels than passive RFID tags. Currently, active RFID tagsimplement batteries that have a life expectancy of up to ten years. Invarious embodiments, active RFID tags (e.g., 202) are embedded within acoating 204 applied to a component 206 of a vehicle. Semi-passive RFIDtags also have their own power source, but the battery only powers theRFID tag's microchip and is not used for broadcasting of a signal. Aswith passive RFID tags, the power to broadcast a signal is received fromthe RF energy emitted by an RFID tag reader. As likewise used herein, amarker reader is defined herein as any apparatus or group oftechnologies that are operable to read an identifier associated with amarker. Likewise, a vehicle component is defined as any individual partof, or sub-assembly of a vehicle, including but not limited to internaland external body panels, structural and suspension components, andmechanical assemblies such as a drivetrain.

FIG. 3 is a simplified illustration of a plurality of markers 302randomly applied to a vehicle component 306 in accordance with anembodiment of the disclosure. In this embodiment, a plurality of markers302 is suspended within a coating 304, which is then applied to acomponent 306 of a vehicle. It will be appreciated that the applicationof the coating 304 to the vehicle component 306 would result in theplurality of markers 302 being embedded within the coating 304.

FIG. 4 is a simplified illustration of a plurality of markers 402applied to a predetermined location on a vehicle component 406 inaccordance with an embodiment of the disclosure. In this embodiment,each of a plurality of markers 402 are applied to a predeterminedlocation of a component 406 of a vehicle and a coating 404 is thenapplied. Skilled practitioners of the art will realize that theapplication of a coating 404 after the plurality of markers 402 areapplied to their respective predetermined locations will embed theplurality of markers 402 within the coating 404. In one embodiment, eachof the plurality of markers 402 has a unique identifier.

FIG. 5 is a simplified illustration of the application of a plurality ofmarkers 502 applied to a predetermined location on a vehicle component506 in accordance with an embodiment of the disclosure. In thisembodiment, a plurality of markers 502 are transferred to a plurality ofpredetermined locations on a component 506 of a vehicle through theimplementation of a transfer sheet 508. Subsequent to their application,a coating is applied to the component 506, thereby embedding theplurality of markers 502 within the coating.

FIG. 6 is a simplified illustration of a vehicle marker processingsystem 618 as implemented in accordance with an embodiment of thedisclosure. In various embodiments, a first plurality of markers 604 isembedded in a coating applied to a component of a first vehicle 602 anda second plurality of markers 608 is embedded in a coating applied to acomponent of a second vehicle 608. In these and other embodiments, thefirst vehicle 602 may strike the second vehicle 608 in the course of anaccident. In the case of a hit-and-run accident, the first vehicle 602may leave 642 the scene of the accident. In one embodiment, markers 610from the first vehicle 602 are left at the scene of the accident. Inanother embodiment, one or more markers 604 from the first vehicle 602become transferred markers 620 upon impact with the second vehicle 608.In one embodiment, markers 610 from the first vehicle 602 left at thescene of the accident are read with a portable or handheld marker reader614 operated by an accident investigator 612. In another embodiment, thesecond vehicle 608 is passed through a stationary marker reader 616 toread the transferred markers 620 from the first vehicle 602.

The marker identifiers 610 are read by the portable marker reader 614and the transferred markers 620 read by the stationary marker reader 616are then processed by a vehicle marker processing system 618, whichcomprises a marker analysis module 148. In various embodiments, thevehicle marker processing system 618 accesses one or more informationrepositories to determine the identity of the first vehicle 602. As anexample, the vehicle marker processing system 618 may access a vehicleinformation repository 622 operated by a vehicle registration agency, ora driver information repository 630 operated by a law enforcement agency628. In one embodiment, prior damage and any related repairs to thesecond vehicle 608 is determined by reading the identifier of the secondvehicle's markers 606, which are then used to query a vehicle historysystem 638, which comprises a vehicle repair history informationrepository 640. In one embodiment, the vehicle history informationrepository 640 comprises repair history information cross-referenced tocomponent information provided by one or more vehicle componentmanufacturers 624, each of which maintains a vehicle componentinformation repository 626. In another embodiment, the vehicle markerprocessing system 618 may use network 162 to access one or more vehiclecomponent information repositories 626 and cross-reference theinformation they provide to the information provided by the vehiclehistory system 638. In one embodiment, the information provided by eachof the vehicle component information repositories 626 is certified by acomponent certification system 632, which in turn comprises a componentcertification module 636 and a component certification informationrepository 634. By comparing the information provided by the vehiclehistory system 638 to the marker identifiers 610, 620 read by markerreaders 614, 616, the vehicle marker processing system 618 candifferentiate between reported damage and repairs and apparent newdamage caused by the first vehicle 602.

FIG. 7 is a simplified illustration of a plurality of markers 702embedded in a coating applied to a plurality of vehicle 706 componentsin accordance with an embodiment of the disclosure. In this embodiment,a plurality of markers 702 is applied to a plurality of components ofvehicle 706. In one embodiment, the identifier of each of the pluralityof markers is indexed to information related to the vehicle 706. As anexample, information relating to the vehicle 706 may comprise a VehicleIdentification Number (VIN), which in turn is related to otherinformation related to the vehicle, such as its registered owner, itsdate of manufacture, as well as its make and model. In one embodiment, adatabase comprises such information related to the vehicle 706, which inturn is indexed to at least one identifier of the plurality of markers702. In another embodiment, each of the plurality of markers 702 appliedto each individual component of the vehicle 706 has the same identifier.In yet another embodiment, the plurality of markers 702 applied to eachindividual component of the vehicle 706 has a different identifier. Instill another embodiment, each of the plurality of markers 702 appliedto each individual component of the vehicle 706 has a unique identifier.

FIG. 8 is a simplified illustration of a stationary marker reader 616 asimplemented in an embodiment of the disclosure. In this embodiment, avehicle 706 that was involved in an accident with another vehicle ispassed through a stationary marker reader 616. As the vehicle 706 ispassed through the stationary maker reader 616, the identifiers of boththe vehicle's original markers 702 and the identifiers of anytransferred markers 804 are read. In one embodiment, the stationarymarker reader 616 is implemented to map the location of an identifierassociated with an original marker 702, and the location of anidentifier associated with a transferred marker 804, on a component ofthe vehicle 706. In another embodiment, the mapping of the identifierassociated with an original marker 702 in relation to the location of anidentifier associated with a transferred marker 804 provides informationrelating to the accident the vehicle 706 was involved in. As an example,the vehicle 706 may have been involved in a hit-and-run accident thatwas caused by another vehicle. It will be appreciated that in many casesit would be difficult to determine the identity of the vehicle thatcaused the accident if there were no eyewitnesses. However, if thevehicle causing the accident comprised markers embedded within a coatingof its components, then some of the markers may be transferred to theother vehicle at the time of impact. The identifiers of thesetransferred markers 804 are then read by the stationary marker reader616. In one embodiment, a database comprises information relating tovehicles, which in turn is indexed to the identifiers of markers appliedto their respective components. Accordingly, the identity of the vehiclecausing the hit-and-run accident can be determined by querying thedatabase with the identifier of a transferred marker 804.

In one embodiment, the vehicle is scanned at predetermined intervals andthe results of the scan are compared to the results of prior scans todetermine if there has been unreported damage to the vehicle betweenscans. As an example, a vehicle may be scanned during a yearlyinspection and the results compared to the results of the last yearlyscan of the vehicle. The results of the comparison can then be comparedto a database of reported damage or repairs. It will be appreciated thatscans indicating unreported damage or repairs may provide the basis forfurther investigation into the reason for the damage or repairs notbeing reported.

FIG. 9 is a generalized flowchart of the operation of a vehicle markerprocessing system as implemented in accordance with an embodiment of thedisclosure to provide vehicle accident information. In this embodiment,accident marker scan operations are begun in block 902, followed bydetermining vehicle identification information in block 904. As anexample, the Vehicle Identification Number (VIN), license plate number,or vehicle registration information may be determined. The vehicleinformation is then used in block 906 to retrieve associated vehicleidentification information. As an example, the VIN may be used to querya database containing vehicle owner identity information. In oneembodiment, a database comprises vehicle information that is indexed tothe identifier of markers applied to its respective components. Thevehicle is then scanned with a marker reader in block 908 as describedin greater detail herein to read the identifiers of markers embedded incoatings applied to a component of the vehicle. In one embodiment, astationary marker reader is implemented to read marker identifiers. Inanother embodiment, a portable or handheld marker reader is implementedto read marker identifiers. A determination is then made in block 912whether the marker identifier has been previously read. As an example,multiple markers may have the same identifier, all associated with apredetermined vehicle's information. As another example, each of themarkers applied to an individual component of a vehicle may have thesame identifier. As yet another example, the identifier of an individualmarker may have already been read.

If it is determined in block 912 that the identifier of a marker hasbeen previously read, then the process continues, proceeding with block908. Otherwise, the identifier of the marker is compared to thepreviously determined vehicle identification information in block 914. Adetermination is then made in block 916 whether the read identifier isassociated with the vehicle being scanned. If so, then the identifier ofthe marker is logged in block 918, signifying that it is associated withthe vehicle being scanned, and the process continues, proceeding withblock 908. Otherwise, the identifier of the marker is logged in block920, signifying that it is not associated with the vehicle beingscanned, and the process continues, proceeding with block 908.

However, if it is determined in block 910 that a marker identifier hasbeen not been read, then a determination is made in block 922 whetherscanning of the vehicle to read marker identifiers is complete. If not,the process continues, proceeding with block 908. Otherwise, adetermination is made in block 924 whether any marker identifiers wereread during the scanning operation. If not, then a report is generatedin block 926 that no marker identifiers were read and accident markeroperations are ended in block 932.

However, if it is determined in block 924 that marker identifiers wereread, then information sources are queried in block 928 for markeridentifiers not associated with identification information related tothe vehicle being scanned. As an example, the vehicle being scanned mayhave been involved in a hit-and-run accident that was caused by anothervehicle. If the vehicle causing the accident comprised markers embeddedwithin a coating of its components, then some of the markers may havebeen transferred to the scanned vehicle at the time of impact. Theidentifiers of these transferred markers are then read by the markerreader. In one embodiment, a database comprises information relating tovehicles, which in turn is indexed to the identifiers of markers appliedto their respective components. Accordingly, the identity of the vehiclecausing the hit-and-run accident can be determined by querying thedatabase with the identifier of a transferred marker. The results of thequeries are then reported in block 930 and accident marker operationsare ended in block 932.

FIG. 10 is a simplified illustration of a stationary marker reader 616as implemented in an embodiment of the disclosure to detect priorvehicle repairs. In this embodiment, a plurality of readable markers1002 is applied to a plurality of components of vehicle 706. In oneembodiment, the identifier of each of the plurality of markers isindexed to information related to the vehicle 706. As an example,information relating to the vehicle 706 may comprise a VehicleIdentification Number (VIN), which in turn is related to otherinformation related to the vehicle, such as its registered owner, itsdate of manufacture, as well as its make and model. In one embodiment, adatabase comprises such information related to the vehicle 706, which inturn is indexed to at least one identifier of the plurality of readablemarkers 1002.

The vehicle 706 is then passed through a stationary marker reader 616.As the vehicle 706 is passed through the stationary maker reader 616,the identifiers of the plurality of readable markers 1002 are read andmapped to their location on vehicle component 1010. Unreadable markers1004 are likewise mapped to their location on vehicle component 1010. Inone embodiment, the mapping of the unreadable markers 1004 indicates adamaged, and subsequently repaired, area of component 1010. In anotherembodiment, the ratio of readable markers 1002 to unreadable markers1004 indicates the percentage of component 1010 that was damaged andsubsequently repaired. In yet another embodiment, the mapping of theunreadable markers 1004 in relation to the location of the plurality ofreadable markers 1002 provides information relating to an accident thevehicle 706 was involved in.

FIG. 11 is a simplified illustration of a stationary marker reader 616as implemented in an embodiment of the disclosure to verify vehiclerepair history. In this embodiment, a plurality of original markers 1102is applied to a plurality of components of vehicle 706. In oneembodiment, the identifier of each of the plurality of markers isindexed to information related to the vehicle 706. In one embodiment, adatabase comprises such information related to the vehicle 706, which inturn is indexed to at least one identifier of the plurality of originalmarkers 1102.

The vehicle 706 is then passed through a stationary marker reader 616.As the vehicle 706 is passed through the stationary maker reader 616,the identifiers of the plurality of original markers 1102 are read andmapped to their location on vehicle 706. At the same time, theidentifiers of non-original markers 1104, corresponding to vehiclecomponent 1110, are likewise read and mapped to their location onvehicle 706. In one embodiment, the mapping of the non-original markers1104 indicates that component 1110 is a replacement component as itsidentifiers are all associated with component 1110. In anotherembodiment, the ratio of original markers 1102 to non-original markers1104 indicates the percentage of vehicle 706 that is not original. Inyet another embodiment, the mapping of the non-original markers 1104 inrelation to the location of the plurality of original markers 1102provides information relating to an accident the vehicle 706 wasinvolved in.

FIG. 12 is a generalized flowchart of the operation of a vehicle markerprocessing system as implemented in accordance with an embodiment of thedisclosure to verify vehicle repair information. In this embodiment,vehicle component history scan operations are begun in block 1202,followed by determining vehicle identification information in block1204. As an example, the Vehicle Identification Number (VIN), licenseplate number, or vehicle registration information may be determined. Thevehicle information is then used in block 1206 to retrieve associatedcomponent history information. As an example, the VIN may be used toquery a database containing reported vehicle repair information whichfurther comprises vehicle component information. In one embodiment, adatabase comprises vehicle component information that is indexed to theidentifier of markers applied to its respective components. The vehicleis then scanned with a marker reader in block 1208 as described ingreater detail herein to read the identifiers of markers embedded incoatings applied to a component of the vehicle. In one embodiment, astationary marker reader is implemented to read marker identifiers. Inanother embodiment, a portable or handheld marker reader is implementedto read marker identifiers. A determination is then made is block 1212whether the marker identifier has been previously read. As an example,multiple markers may have the same identifier, all associated with apredetermined vehicle component. As another example, the identifier ofan individual marker may have already been read.

If it is determined in block 1212 that the identifier of a marker hasbeen previously read, then the process continues, proceeding with block1208. Otherwise, the identifier of the marker is compared to thepreviously determined vehicle component history information in block1214. A determination is then made in block 916 whether the readidentifier is listed in the component history information for thevehicle being scanned. If so, then the identifier of the marker islogged in block 918, signifying that it is listed in the componenthistory information for the vehicle being scanned, and the processcontinues, proceeding with block 1208. Otherwise, the identifier of themarker is logged in block 920, signifying that it is not listed in thecomponent history information for the vehicle being scanned, and theprocess continues, proceeding with block 1208.

However, if it is determined in block 1210 that a marker identifier hasbeen not been read, then a determination is made in block 1222 whetherscanning of the vehicle to read marker identifiers is complete. If not,the process continues, proceeding with block 1208. Otherwise, adetermination is made in block 1224 whether any marker identifiers wereread during the scanning operation. If not, then a report is generatedin block 1226 that no marker identifiers were read and accident markeroperations are ended in block 1232.

However, if it is determined in block 1224 that marker identifiers wereread, then information sources are queried in block 1228 for markeridentifiers not listed in the available component history information.As an example, a previous repair to the vehicle being scanned may nothave been reported. By using the marker identifiers not listed in theavailable component history information for queries, additionalinformation relating to the previous repair may be discovered and thenappended to the available component history information. The results ofthe queries are then reported in block 1230, reconciled against theavailable component history information, and vehicle component historyscan operations are ended in block 1232.

FIG. 13 is a generalized illustration of a vehicle repair history asimplemented in accordance with an embodiment of the invention. In thisembodiment, a vehicle repair history 1302 comprises vehicle andcomponent information related to the identifier of a marker embeddedwithin a coating applied to a component of a vehicle. The Vehicle RepairHistory 1302 comprises the year 1304 the vehicle was manufactured(“2009”), its manufacturer 1306 (“Reliance”), its model 1308(“Impacta”), and its Vehicle Identification Number 1310(“FJ235895KK4525L23”). The Vehicle Repair History 1302 likewisecomprises date 1312 of reported repairs, repaired or replaced components1314, the part number 1316 of each component, the manufacturer 1318 ofthe component, and the identifier 1320 of the marker embedded in acoating applied to the component. Likewise, the Vehicle Repair History1302 comprises the supplier 1320 of the component, the name of thevehicle repair 1324 entity, and vehicle repair 1324 entity's location1326. In various embodiments, the information contained in the VehicleRepair History 1302 is generated by reading the identifiers of markersembedded in a coating applied to various components of a vehicle, andthen indexing the read identifiers to related vehicle information asdescribed in greater detail herein.

It will be apparent to those of skill in the art that the provision of aVehicle Repair History 1302 provides a significant level of detailrelated to the repair history of a vehicle. As an example, the repair1328 performed on Feb. 14, 2012 was performed by a dealer (“MemphisReliance”) of the vehicle manufacturer (“Reliance”), using partsmanufactured (“Reliance OEM”) by, or on behalf of, the manufacturer(“Reliance”). By examining the repair record 1330 performed on Feb. 15,2012 it can be surmised that since there is only one days differencebetween repairs 1328 and 1330, and since they both took place inMemphis, Tenn., that the repair entity (“Alignment Plus”) or repair 1330was likely a subcontractor to Memphis Reliance.

As another example, the repair 1332 dated Jul. 8, 2014 indicates that anindependent repair entity (“Dents And More”) performed the repair usinga non-OEM (“Exact Match”) front bumper, a third party (“Monroe”)manufacturer of the shock absorber, and OEM (“Reliance OEM”) frontbumper bracket and bumper brace. Likewise, the location 1326 of repair1332 indicates that the repair was made in Atlanta, Ga. As yet anotherexample, the repair 1334 dated Feb. 16, 2015 indicates that anotherindependent repair entity (“Top Notch Body”) performed the repair usinga non-OEM (“Generic Panels”) left fender, left door skin, lower doorcladding, left fender trim, and lower door trim. Furthermore, all of thenon-OEM components were supplied by Parts Express and the repair wasperformed in Tampa, Fla. Further examination of Vehicle Repair History1302 indicates additional repairs 1336 were made, but not reported bythe repair entity or the supplier of the components. However, thecomponents that were replaced, and their respective part numbers, weredetermined by their corresponding marker identifiers. It will beappreciated that the level of detail embodied by such a Vehicle RepairHistory 1302 provides a comprehensive repair history of a vehicle,whether or not the repairs have been reported by the entity making therepairs.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the disclosure. Accordingly, each block in the flowchartor block diagrams may represent a module, segment, or portion of code,which comprises one or more executable instructions for implementing thespecified logical function(s). In certain alternative implementations,the functions performed in a particular block may occur in an order thatis different than what is noted in the figures. For example, two blocksshown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustrations,and combinations of blocks in the block diagrams and/or flowchartillustrations, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a,” “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof. The term “embodiment” can be used todescribe any aspect, feature, process or step, any combination thereof,and/or any portion thereof, of the disclosure and should not beinterpreted as limiting the scope of the application or claims.

While the disclosure has been described by reference to particularembodiments, such references do not imply a limitation and no suchlimitation is to be inferred. As such, the disclosure includes any andall embodiments having equivalent elements, modifications, omissions,combinations (e.g., of aspects across various embodiments), adaptations,alterations, and equivalents in form and function. As will be furtherappreciated by those skilled in the pertinent arts, the disclosure has anumber of aspects and embodiments, and various embodiments may includeoverlapping features.

For example, the above-discussed embodiments may include softwaremodules that include script, batch, or other executable files for theperformance of certain tasks. These software modules may be stored on amachine-readable or computer-readable storage medium such as a diskdrive. Storage devices used for storing software modules in accordancewith various embodiments may include magnetic floppy disks, hard disks,or optical discs such as CD-ROMs or DVDs. A storage device used forstoring firmware or hardware modules in accordance with an embodimentmay also include a semiconductor-based memory, which may be permanently,removably or remotely coupled to a microprocessor/memory system. Thus,the software modules may be stored within a computer system memory toconfigure the computer system to perform the functions of the module.Other new and various types of computer-readable storage media may beused to store the modules discussed herein. Additionally, those skilledin the art will recognize that the separation of functionality intomodules is for illustrative purposes. Alternative embodiments may mergethe functionality of multiple modules into a single module or may imposean alternate decomposition of functionality of modules. For example, asoftware module for calling sub-modules may be decomposed so that eachsubmodule performs its function and passes control directly to anothersub-module. In addition, each of the referenced components in thisembodiment may be comprised of a plurality of components, eachinteracting with the other in a distributed environment. Furthermore,other embodiments may expand on the referenced embodiment to extend thescale and reach of the system's implementation.

The description of the disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited in the form disclosed. It will be apparent to those of skill inthe art that many modifications and variations are possible withoutdeparting from the scope and spirit of the disclosure, giving fullcognizance to equivalents in all respects.

What is claimed:
 1. A non-transitory computer-readable medium storinginstructions executable by a computer to: obtain marker identificationdata corresponding to an individual vehicle, wherein the markeridentification data includes vehicle identity data stored in a pluralityof markers embedded in a coating, wherein each of the plurality ofmarkers is applied directly to the individual vehicle, wherein at leastone of the plurality of markers is a visual identifier, and the coatingis applied after the plurality of markers are applied and the pluralityof markers embedded in the coating do not protrude from the coating; andcorrelate marker identification data corresponding to the individualvehicle with marker identification data in a database including markeridentification data indexed to a plurality of individual vehicles toprovide identity information and vehicle damage informationcorresponding to the individual vehicle.
 2. The medium of claim 1,wherein at least one of the plurality of markers is readable by a markerreader and the marker reader is operable to map a location of the atleast one readable marker on the individual vehicle.
 3. The medium ofclaim 1, wherein a number of the plurality of the markers are readableby a marker reader and at least one of the markers read by the markerreader is associated with a first vehicle and at least one of themarkers read by the marker reader is associated with a second vehicle.4. The medium of claim 3, wherein reading the at least one of themarkers associated with the first vehicle maps a location of the atleast one marker.
 5. The medium of claim 4, wherein reading the at leastone of the markers associated with the second vehicle maps a location ofthe at least one marker.
 6. The medium of claim 5 wherein the mapping ofthe at least one marker associated with the first vehicle and mapping ofthe at least one marker associated with the second vehicle providesinformation relating to damage incurred by the first vehicle.
 7. Themedium of claim 5 wherein the mapping of the at least one markerassociated with the first vehicle and mapping of the at least one markerassociated with the second vehicle provides information relating todamage incurred by the second vehicle.
 8. A system for providinginformation relating to damage incurred by a vehicle, comprising: adatabase including marker identification data associated with aplurality of individual vehicles; and an analysis module to correlatemarker identification data corresponding to an individual vehicle withthe marker identification data to provide identity information andvehicle damage information corresponding to the individual vehicle;wherein the marker identification data corresponding to the individualvehicle includes data stored in a plurality of markers embedded in acoating, wherein each of the plurality of markers is applied directly tothe individual vehicle, wherein at least one of the plurality of markersis a visual identifier, and the coating is applied after the pluralityof markers are applied and the plurality of markers embedded in thecoating do not protrude from the coating.
 9. The system of claim 8,wherein the visual identifier is a two dimensional barcode.
 10. Thesystem of claim 8, wherein at least one of the plurality of markers isan electromagnetic identifier.
 11. The system of claim 8, wherein atleast one of the plurality of markers is an electro luminescentidentifier.
 12. The system of claim 8, wherein at least one of theplurality of markers is a carbon nanotube signature.
 13. The system ofclaim 8, wherein at least one of the plurality of markers is a radiofrequency identification tag.
 14. A non-transitory computer-readablemedium storing instructions executable by a computer to: associateidentification data with a plurality of individual vehicles; andassociate identification data corresponding to an individual vehiclewith the identification data associated with the plurality of vehiclesto provide identity information and vehicle damage informationcorresponding to the individual vehicle; wherein the identification dataassociated with the individual vehicle includes identity data stored ina plurality of markers embedded in a coating, wherein each of theplurality of markers is applied directly to the individual vehicle,wherein at least one of the plurality of markers is a visual identifier,and the coating is applied after the plurality of markers are appliedand the coating is a finish applied to the individual vehicle such thatthe plurality of embedded markers do not protrude from the finish. 15.The medium of claim 14, wherein each of the plurality of markers appliedto particular component of the individual vehicle has a like identifier.16. The medium of claim 14, wherein each of the plurality of markers areapplied to a different component of the individual vehicle and have adifferent identifier.
 17. The medium of claim 14, wherein each of theplurality of markers applied to a different component of the individualvehicle has a unique identifier.
 18. The medium of claim 14, wherein themarker identification data corresponding to the individual vehicleincludes a vehicle identification number (VIN).
 19. The medium of claim14, wherein the identification data corresponding to the individualvehicle includes registration information.